Fix inference cycle in getattr when a base is an astroid.Attribute #934
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nelfin
force-pushed
the
fix/904-inference-error-on-metaclass-attribute
branch
2 times, most recently
from
eb2e14d to
fdf69e0
Compare
nelfin
force-pushed
the
fix/904-inference-error-on-metaclass-attribute
branch
from
fdf69e0 to
e402894
Compare
Ref pylint-dev#904. `getattr` attempts to find values on `self.ancestors`, which infers each node listed in `self.bases`. Removing or resetting the context passed to ancestors allows it to infer the nodes, but opens up the possibility of cycles through recursive definitions. We should be able to infer the value of the base node correctly as a `ClassDef`. The root of this issue stems from the fact that `infer_attribute` attempts to temporarily set `context.boundnode`, but when unwrapping its changes it sets the `boundnode` to `None` instead of its previous value, which loses state and causes the inference of the `Attribute` node to have a duplicate key: once when looking up the class definition (which should have `boundnode = None`), and once when inferring the (other) attribute value (which should not have `boundnode = None`)
nelfin
force-pushed
the
fix/904-inference-error-on-metaclass-attribute
branch
from
e402894 to
fa3731b
Compare
cdce8p
added
the
pylint-tested
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Steps
Description
Ref #904.
getattrattempts to find values onself.ancestors, whichinfers each node listed in
self.bases. Removing or resetting thecontext passed to ancestors allows it to infer the nodes, but opens up
the possibility of cycles through recursive definitions. We should be
able to infer the value of the base node correctly as a
ClassDef. Theroot of this issue stems from the fact that
infer_attributeattemptsto temporarily set
context.boundnode, but when unwrapping its changesit sets the
boundnodetoNoneinstead of its previous value, whichloses state and causes the inference of the
Attributenode to have aduplicate key: once when looking up the class definition (which should
have
boundnode = None), and once when inferring the (other) attributevalue (which should not have
boundnode = None)Type of Changes
Related Issue
Closes #904